Extended reporting WIP#16741
Conversation
|
We would have to pick another command for this. "Wait for all temperatures and other slowly-changing variables to arrive at their set values if no parameters are specified. See also But I think what you really want to implement is either an extension to |
|
We prefer not to add features that require a pile of strings for all configurations because Melzi boards have a limited amount of space. |
The strings can be shorten if they look a lot, like those on Repetier Firmware M360 or even shorter than those or even report as CSV values like: . Also these will be reported only when |
|
If hosts are doing an I'm not very fond of having these as part of As an alternative, these parameters could (also) be added to the |
|
I think putting the bed/build area reporting under |
28c6bd2 to
ebd2bcc
Compare
39fe6ef to
7aed32d
Compare
b35d361 to
a6009be
Compare
17d3472 to
42fa46c
Compare
|
Rebased and squashed. To update your working copy use the Git Console and the following commands: |
7b92348 to
37176ed
Compare
99c01c8 to
e59bef5
Compare
0ae21d8 to
0286c32
Compare
711a818 to
7c79515
Compare
Co-Authored-By: guruathwal <[email protected]>
Description
Report machine/bed size and x,y & z axis position limits to the host. The host program/controller can auto-configure settings based on the received details.
Benefits
This is helpful for users who do not know much about compiling firmware for serial host controller like Bigtreetech touch screen controllers where bed dimensions and axis movement limits are needed to configure setting like leveling points or checking if the g-code is within machine limits before sending to the machine to avoid accidents and failures.